ODE97: Access 97 Run-Time Application
Incorrectly Uses Access 2000 ExecutableView
products that this article applies to.
This article was previously published under
Q248112
Advanced: Requires expert coding,
interoperability, and multiuser skills.
This article
applies only to a Microsoft Access database (.mdb).
SYMPTOMSWhen you upgrade a computer from Microsoft
Access 97 to Microsoft Access 2000, and an Access 97 run-time
application is subsequently installed, you may receive the
following error message:
The current user account doesn't have
permission to convert or enable this database.
CAUSEYou have installed your Access 97 run-time
application on a computer that was previously upgraded from
Access 97 to Access 2000. When an Access 97 run-time
application is installed on a computer, the setup program
tries to determine if a copy of Access 97 is already installed
on the computer by looking for the following registry key: HKEY_LOCAL_MACHINE\
Software\
Microsoft\
Office\
8.0\
Common\
InstallRoot\
OfficeBin
This key contains the path to the installed copy of
Access 97. If the Setup program finds this key, it does not
install the Access 97 copy of Msaccess.exe, but instead uses
the existing copy. When a computer is upgraded from
Access 97 to Access 2000, the OfficeBin key is not removed and
the Access 2000 version of Msaccess.exe is copied to the
location where Access 97 was previously installed. This leaves
the OfficeBin key pointing to the Access 2000 version of
Msaccess.exe. Because of this, upgrading from Access 97 to
Access 2000, and then installing an Access 97 run-time
application, results in the run-time pointing to the Access
2000 version of the executable.
RESOLUTIONTo workaround this behavior, you must
modify the Setup.stf file that is produced by the ODE Setup
Wizard. This allows any future installations that you perform
by using this Setup.stf file to include the Access 97
executable and supporting files.
WARNING: Modifications to an STF file
should be made by using a backup copy of the file. As a
general rule, modifications to an STF file are not recommended
by Microsoft. However, this is currently the best workaround
for this issue. You can open and edit the Setup.stf
file in Notepad. If you edit the file with Microsoft Excel,
you may see error messages. For additional information about
these error messages, click the article number below to view
the article in the Microsoft Knowledge Base:
111248
OFF: Opening/Saving STF File in Excel May Cause Setup Errors
The following steps show you how to change the STF file:
- In Notepad or another text editor, open the Setup.stf
file that was created by the ODE Setup Wizard.
- Locate the line where:
ObjID is 65 Type is CustomAction and
Data is
"msacccah.dll,GetPathFromReg,""HKEY_LOCAL_MACHINE,Software\Microsoft\Office\8.0\Common\InstallRoot,OfficeBin"""
Change
the word "InstallRoot" to "InstallAccessRT", as follows:
"msacccah.dll,GetPathFromReg,""HKEY_LOCAL_MACHINE,Software\Microsoft\Office\8.0\Common\InstallAccessRT,OfficeBin"""
NOTE: This line searches for the Office
folder. If you change the key, it should not find anything
unless you have installed a run-time application by using
this technique already. Although InstallAccessRT can be
virtually any name that you want to use, ensure that the
name is the same in both steps 2 and 3.
- Locate the line where:
ObjID = 85 Type = AddRegData and Data
=
"""LOCAL"",""Software\Microsoft\Office\8.0\Common\InstallRoot"",""OfficeBin"",""%70"","""""
Change the word "InstallRoot" to "InstallAccessRT" (the
same word that you used in step 2), as follows:
85"""LOCAL"",""Software\Microsoft\Office\8.0\Common\InstallAccessRT""
,""OfficeBin"",""%70"","""""
- Locate the line where:
ObjID = 320 Type = InstallShared and
Data = "Access Runtime
Files,msaccess_exe,MSACCESS80,Office,1325 "
NOTE: This line writes a key to the
registry under HKEY_LOCAL_MACHINE\Software\Microsoft\Shared
Tools
Change the word "MSACCESS80" to "MSACCESS80RT",
as follows:
"Access Runtime
Files,msaccess_exe,MSACCESS80RT,Office,1325 "
- Save and close the Setup.stf file.
For Systems That Already Have This IssueIf you have
already installed your Access 97 run-time application on a
computer and it now has the symptoms described in the
"Symptoms" section, you should first remove the Access 97
run-time application, and then reinstall it with the modified
Setup.stf file. To remove the application, follow these steps.
NOTE: The following steps will remove
the Access 97 run-time installation including the Access
database. If you want to preserve the database, make a copy of
it, and save it to another folder for safe
keeping. NOTE: Because there are
several versions of Microsoft Windows, the following steps may
be different on your computer. If they are, see your product
documentation to complete these steps.
- Click Start, point to
Settings, and then click Control
Panel.
- Click Add/Remove Programs.
- In the Add/Remove Programs dialog box,
click the name of the Access 97 run-time application, and
then click Add/Remove. The application's
Setup program starts.
- Click Remove All.
You are now
ready to install the Access 97 run-time application with the
modified Setup.stf file.
REFERENCESFor additional information on a similar
issue that involves installing Access 2000 over an existing
Access 97 run-time application, click the article number below
to view the article in the Microsoft Knowledge Base:
248913
ODE97: Convert or Enable Message when Opening Access 97
Runtime Application After Installing Office 2000
The information in this article applies to:
- Microsoft Office 97 Developer Edition
- Microsoft Access 2000
Last Reviewed: |
5/9/2003 (2.0)
|
Keywords: |
kberrmsg kbhowto
KB248112 |
|